Flexible arbitration scheme for multi endpoint atomic accesses in multicore systems

ABSTRACT

The MSMC (Multicore Shared Memory Controller) described is a module designed to manage traffic between multiple processor cores, other mastering peripherals or DMA, and the EMIF (External Memory InterFace) in a multicore SoC. The invention unifies all transaction sizes belonging to a slave previous to arbitrating the transactions in order to reduce the complexity of the arbitration process and to provide optimum bandwidth management among all masters. Two consecutive slots are assigned per cache line access to automatically guarantee the atomicity of all transactions within a single cache line. The need for synchronization among all the banks of a particular SRAM is eliminated, as synchronization is accomplished by assigning back to back slots.

CLAIM OF PRIORITY

This application claims priority under 35 U.S.C. 119(e)(1) toProvisional Application No. 61717831 filed 24 Oct. 2012.

TECHNICAL FIELD OF THE INVENTION

The technical field of this invention is multicore processing systems.

BACKGROUND OF THE INVENTION

In a multi-core coherent system, multiple central processing unit (CPU)and system components share the same memory resources, such as on-chipand off-chip RAMs. Ideally, if all components had the same cachestructure, and would access shared resource through cache transactions,all the accesses would be identical throughout the entire system,aligned with the cache block boundaries. But usually, some componentshave no caches, or, different components have different cache blocksizes. For a heterogeneous system, accesses to the shared resources canhave different attributes, types and sizes. On the other hand, theshared resources may also be in different format with respect to bankingstructures, access sizes, access latencies and physical locations on thechip.

To maintain data coherency, a coherence interconnect is usually added inbetween the master components and shared resources to arbitrate amongmultiple masters' requests and guarantee data consistency when datablocks are modified for each resource slave. With various accesses fromdifferent components to different slaves, the interconnect usuallyhandles the accesses in a serial fashion to guarantee atomicity and tomeet slaves access requests. This makes the interconnect the accessbottleneck for a multi-core multi-slave coherence system.

To reduce CPU cache miss stall overhead, cache components could issuecache allocate accesses with the request that the lower level memoryhierarchy must return the “critical line first” to un-stall the CPU,then the non-critical line to finish the line fill. In a shared memorysystem, to serve one CPU's “critical line first” request couldpotentially extend the other CPU's stall overhead and reduce the sharedmemory throughput if the memory access types and sizes are notconsidered. The problem therefore to solve is how to serve memoryaccesses from multiple system components to provide low overall CPUstall overhead and guarantee maximum memory throughput.

Due to the increased number of shared components and expended shareablememory space, to support data consistency while reducing memory accesslatency for all cores while maintaining maximum shared memory bandwidthand throughput is a challenge. Speculative memory access is one of theperformance optimization methods adopted in hardware design.

SUMMARY OF THE INVENTION

The invention described unifies all transaction sizes belonging to aslave previous to arbitrating the transactions in order to reduce thecomplexity of the arbitration process and to provide optimum bandwidthmanagement among all masters.

Two consecutive slots are assigned per cache line access toautomatically guarantee the atomicity of all transactions within asingle cache line.

The need for synchronization among all the banks of a particular SRAM iseliminated, as synchronization is accomplished by assigning back to backslots.

BRIEF DESCRIPTION OF THE DRAWING

These and other aspects of this invention are illustrated in thedrawing, in which:

The figure shows a high level block diagram of the Multicore SharedMemory Controller.

DETAILED DESCRIPTION OF PREFERRED EMBODIMENTS

The MSMC (Multicore Shared Memory Controller) is a module designed tomanage traffic between multiple processor cores, other masteringperipherals or DMA, and the EMIF (External Memory InterFace) in amulticore System on Chip (SoC). The MSMC provides a shared on-chipmemory that can be used either as a shared on-chip SRAM or as a cachefor external memory traffic. The MSMC module is implemented to support acluster of up to eight processor cores and be instantiated in up to foursuch clusters in a multiprocessor SoC. The MSMC includes a MemoryProtection and Address eXtension unit (MPAX), which is used to convert32-bit virtual addresses to 40-bit physical addresses, and performsprotection checks on the MSMC system slave ports. The following featuresare supported in one implementation of the MSMC:

-   -   Configurable number of CPU cores,    -   One 256-bit wide EMIF master port,    -   One 256-bit wide System Master port,    -   Two 256-bit wide System Slave ports,    -   CPU/1 frequency operation in MSMC,    -   Level 2 or 3 SRAM shared among connected processor cores and        DMA,    -   Write transaction merge support for SRAM accesses,    -   Supports 8 SRAM banks, each can be accessed in parallel every        clock cycle,    -   Each SRAM bank has 4 virtual sub-banks,    -   Memory protection for EMIF and MSMC SRAM space accesses from        system masters,    -   Address extension from 32 bits to 40 bits for system master        accesses to shared memory and external memory,    -   Optimized support for prefetch capabilities,    -   System trace monitor support and statistics collection with        CP_Tracer (outside MSMC) and AET event export,    -   EDC and scrubbing support for MSMC memory (SRAM and cache        storage),    -   Firewall memory protection for SRAM space and DDR space,    -   MPAX support for SES and SMS,    -   MPAX provides 32 to 40 bit address extension/translation,    -   MPAX includes a Main TLB and uTLB memory page attribute caching        structure,    -   Coherency between A15 L1/L2 cache and EDMA/IO peripherals        through SES/SMS port in SRAM space and DDR space.

The figure shows a high level view of the MSMC module that includes themain interfaces, memory, and subunits.

The MSMC has a configurable number of slave interfaces 101 for CPUcores, two full VBusM slave interfaces 102 and 103 for connections tothe SoC interconnect, one master port 104 to connect to the EMIF and onemaster port 105 to connect to the chip infrastructure.

Each of the slave interfaces contains an elastic command buffer to holdone in-flight request when the interface is stalled due to loss ofarbitration or an outstanding read data return. During that time, theother slave interfaces can continue to field accesses to endpoints thatare not busy.

The invention described implemented in a Multicore Shared MemoryController, (MSMC) implements the following features:

Segmentation of non-cacheline aligned requests for non-cacheable butshared transactions to enable parallel transactions to multiple slavesin atomic fashion;

Segmentation size is optimized to slave access request and master cacheline size;

In the MSMC platform, a shared on-chip SRAM is implemented as scratchmemory space for all master components. This SRAM space is split into 8parallel banks with the data width being the half of the cache linesize. The segmentation boundary for the on-chip SRAM space is set toalign with the bank data width size, and the MSMC central arbiter foron-chip SRAM banks reserves two back-to-back slots for each commandworth of a single cache line fill;

MSMC also handles all masters' accesses to the off-chip DRAM space. Theoptimum access size is equal or larger than the cache line size. MSMCsegmentation logic takes this slave request into account to split thecommands on the cache line boundaries. The MSMC central arbiter foroff-chip DRAM reserves two back-to-back slots for two commands worth oftwo cache line fills;

If the command is less than a cache line size and couldn't fill in theclock cycles required for a full cache line allocate command,segmentation logic inserts a dummy command cycle to fill in the dummybank slot;

Due to the number of cores, size of on-chip SRAM and number of banks,the physical size of MSMC doesn't allow the central arbiter function tobe completed in a single execution clock cycle. With two reserved cyclesper command, the second cycle will take the decision from the firstcycle, therefore the central arbiter doesn't need to be done in a singlecycle;

Memory access order is set to make sure the maximum memory bandwidth isutilized;

Reverse write dataphases before committing if the critical line firstrequest forces the higher address location dataphase to be writtenfirst;

Reverse read returns if the higher address location dataphase isrequired to be to returned first by the component;

Performance benefit in virtually banked SRAM memories since steps arealways monotonic between virtual banks;

Allows simplified virtual banking arbitration by effectively halving thenumber of virtual banks, and the MSMC central arbiter for off-chip DRAMreserves two back-to-back slots for two commands worth of two cache linefills;

Each component has a dedicated return buffer which gets force-linearinfo for read return;

Reference look-ahead message in distributed data return storage allowingthis;

Off-chip memory return without force-linear returns in different order;

Each CPU has its own return buffer. The entry number of the returnbuffer is configurable to address different round trip latencies;

With the addition of return buffer, MSMC passes each CPU's memory accessrequest to the slaves without holding and treats them as speculativeread requests. Meanwhile, if the request is to shared memory space, MSMCissues snoop request to the corresponding cache components. When bothmemory response and snoop response are returned, MSMC orders theseresponses in the return buffer per CPU bases according to dataconsistence rule;

To keep a record of the data access ordering for correct data coherencesupport without performance degradation, pre-data messages in all casesare generated and saved in each entry of return buffer before the memoryrequest and snoop request are issued. This ensures optimum performanceof both coherent and non-coherent accesses and avoids protocolhazarding. The metadata and status bits in each entry are

-   -   a. Original memory request identification number;    -   b. Ready bit acts are time stamp for the status match of the        corresponding entry to kick off the snoop response waiting        period. This is very important since MSMC support hit-under-miss        if current request overlaps with a previous in-flight memory        access. This bit is used to accumulate the correct snoop        response sequence for data consistency;    -   c. Force linear bit indicates the order of dataphase returns to        support each CPU's cache miss request for performance purposes;    -   d. Shareable bit which indicates if the snoop request therefore        the responses will be counted by the return buffer or not;    -   e. Memory read valid bit indicates the corresponding memory        access responses has landed in the return buffer entry;    -   f. Snoop response valid bit indicates the corresponding snoop        access responses has landed in the return buffer entry;    -   g. Memory access error bit indicates a memory access error has        occurred;    -   h. Snoop response error bit indicates a snoop response error has        occurred;

The return buffer also records the write respond status for coherencewrite hazard handling.

Both error response from memory access and snoop response will result inan error status return to the initiating master component.

To support fragmented read returns, byte strobes are stored on a perbyte bases. Each bit represents whether a byte lane worth of data isvalid or not. All byte lanes have to be merged before valid the bit isasserted.

What is claimed is:
 1. A Multicore Shared Memory Controller (MSMC)comprising: a plurality of CPU interfaces for connection to respectivecentral processing units for receiving CPU transaction requests; atleast one slave interface for connection to a corresponding slave deviceserving as a shared resource; a multicore shared memory controllerdatapath connected to said plurality of CPU interfaces and said at leastone slave interface, said multicore shared memory controller datapathoperable to receive CPU transaction requests from central processingunits via a corresponding CPU interface, arbitrate between mastercomponents and shared resources and operable to enforce data consistencywhen data blocks are modified for a resource slave, reserve two back toback slots for each command processing a single cache line fill requestfrom one of said plurality of CPU interfaces, and insert a dummy commandcycle if a memory access from one of the plurality of CPU interfacesrequests less than a cache line size.
 2. The Multicore Shared MemoryController of claim 1, wherein: said multicore shared memory controllerdatapath is further operable to segment non cacheline aligned receivedCPU transaction requests.
 3. The Multicore Shared Memory Controller ofclaim 1, wherein: said multicore shared memory controller datapath isfurther operable to perform parallel transactions to multiple slaves inan atomic fashion.
 4. The Multicore Shared Memory Controller of claim 1,further comprising: a shared on chip memory; and said multicore sharedmemory controller datapath is further operable to employ said shared onchip memory as scratch memory for all master components, with the memoryaddressing space segmented into a plurality of parallel banks where thedata width is sized to be half of the cache line size, and thesegmentation boundaries for the on chip memory is aligned with the bankdata width size.
 5. The Multicore Shared Memory Controller of claim 1,further comprising: an off chip memory interface; and said multicoreshared memory controller datapath is further operable to process allmaster's accesses to off chip memory via said off chip memory interfacewith an optimum access size equal to or larger than the cache line size,and to segment the access commands to the off chip memory on cache lineboundaries.
 6. The Multicore Shared Memory Controller of claim 5,wherein: said multicore shared memory controller datapath is furtheroperable to reserve two back to back slots for two commands processingtwo cache line fills.